home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
QRZ! Ham Radio 8
/
QRZ Ham Radio Callsign Database - Volume 8.iso
/
pc
/
files
/
t_unix
/
j109lxa4.tar
/
README.linux
< prev
next >
Wrap
Text File
|
1994-06-04
|
4KB
|
89 lines
JNOS 1.09 for Linux
ALPHA.4 Release of 94.06.04
Is it me or am I taking longer and longer to get these out? I lost some three
months because I was spending days and nights both working on a client's
system. Anyway, it's finaly here. README-ALPHA.4 contains the highlights of
this release.
Building nos
------------
As you've probably noticed, this is a full release instead of a set of
patches. jnos08df.zip is getting hard to find. (I should take the hint...)
1. Unpack this archive. You don't need any other files, except possibly
ncurses 1.8. The 1.8.1 release provided with SLS and Slackware is usable,
but ncurses 1.8.5 is preferred.
ftp.netcom.com:/pub/zmbenhal/ncurses/1.8.5.tgz
2. Edit config.h and turn off the options you don't want. Turn *on* options
at your own risk... generally, if it's not defined, it's not tested or
ported (or working, as with the callserver code).
3. Edit Makefile and check for anything you might want to change there. The
most likely are:
ICURSES: I used Slackware 1.1.x's /usr/include/ncurses mechanism this time.
The Makefile tells you what to change for the standard ncurses install
mechanism.
DEBUG: comment out if you like to live dangerously :-) nos is about 2.5MB
with this on, and is debuggable. Without it, the size is around 600K
but you're going to have trouble figuring out why if it blows up in
your face. (This depends on the options you compile in.) Replacing
it with "DEBUG = -s" makes nos about 400K but the result can't be
debugged at all. All of this is symbol table, none of it is code;
building with -g3 and then running "strip nos" will give you the 400K
binary.
4. Type "make". After a while (11 minutes on my 24MB EISA 486DX2/66; closer
to 40 minutes on my 12MB 386/33) this will result in a file called "nos". Or
at least it should...
Installing
----------
WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING
In this release, I have switched to the DOS-compatible paths in place of the
paths that I inherited from the existing "#ifdef UNIX" stuff. If you are
replacing an existing installation, you must move things around or use a
config file.
The good news is, I enabled the "-f <configfile>" option in ALPHA.2 without
telling anyone :-) Use "nos -f compat.cfg" to start JNOS if you want to use
the old directory structure and file names.
For newcomers, the advantage is that all the paths and filenames now match the
DOS version; the startup file is "autoexec.nos", not "startup.nos" like the
old version wanted. Since one of my intents is to mirror a DOS configuration
as closely as possible, I decided to lose the Unixy names I inherited with the
-DUNIX code.
The result is that JNOS should configure much the same way the DOS version
does. Remember that it's 1.09, not 1.10x. There are differences, however, in
the "attach" command; these are unavoidable (well, no, they're not, but
running setserial to map the port/IRQ to Linux devices is a bit silly...).
attach asy /dev/ttyS? - ...
/dev/ttyS? is a serial port. COM1 is ttyS0, etc. (Avoid the cua? ports; for
some reason, they can give NOS heartburn. This may have changed with the
"new" serial drivers, but I run 1.0.9 here.) You should use "-" as the third
argument to "attach", just in case I think of a use for it later.
Your NOS installation can be placed in any directory; paths will be
interpreted relative to your current directory when you run nos. Since this
is Unix (well, Linux :-) you should not expect drive letters to work, nor
should you expect file and directory names to ignore upper/lower case.
autoexec.kf8nh is my autoexec file, slightly modified because I like to keep
things like routes in separate files but I combined them in for the sample
file.